Skip to content

fix: widen PyJWT version constraint to allow 2.11+#523

Merged
MichaelGHSeg merged 1 commit intomasterfrom
fix/522-widen-pyjwt-constraint
Mar 2, 2026
Merged

fix: widen PyJWT version constraint to allow 2.11+#523
MichaelGHSeg merged 1 commit intomasterfrom
fix/522-widen-pyjwt-constraint

Conversation

@MichaelGHSeg
Copy link
Contributor

Summary

  • Changes PyJWT~=2.10.1 (>=2.10.1, <2.11) to PyJWT~=2.10 (>=2.10, <3) in setup.py
  • Matches the version constraint pattern used by the other dependencies (requests~=2.7, backoff~=2.1, python-dateutil~=2.2)
  • SDK only uses jwt.encode() with RS256, which is a stable API surface

Fixes #522

Test plan

  • Verified pip install resolves to PyJWT 2.11.0 with the new constraint
  • All 72 non-OAuth tests pass (7 OAuth tests fail on main too — missing cryptography package in test env, pre-existing)

🤖 Generated with Claude Code

Changes PyJWT~=2.10.1 (>=2.10.1, <2.11) to PyJWT~=2.10 (>=2.10, <3)
to match the pattern used by other dependencies in setup.py.

Fixes #522

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@MichaelGHSeg MichaelGHSeg merged commit c0574b7 into master Mar 2, 2026
7 checks passed
@MichaelGHSeg MichaelGHSeg deleted the fix/522-widen-pyjwt-constraint branch March 2, 2026 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Allow PyJWT version 2.11

2 participants